Swift Outward (MT)

This section describes the working of Swift Outward (MT) message flow.

Swift Outward uses the existing SWIFT.OUT TSA service. A parameter table (SWIFT.ALLIANCE.PARAM) is required to set up the details for both the outward file type or queue parameters. Currently, Swift processing can handle File format and Queue processing.

The table below describes the field available in the SWIFT.ALLIANCE.PARAM table.

Field	Description
Out Msg Format	This can be either RJE or DOS-PCC as per the user requirement.
Mq Enable	For normal FTP message processing, this is set as None. This field is set to Outward when messages are processed through MQ Server and additional fields will populate and should be entered as per the user requirement.
Mq Conn Factory	Defines the connection factory details to process the Alliance outgoing message into the Out queue defined in the MQ.OUT.QUEUE.NAME.
Mq Out Queue Name	Defines the Out queue name.
Guard Queue Name	Defines the guard queue details. It is used to get the Outgoing message if Out queue is not ready.
Time to Live	Defines the time to retain the message in the Guard queue.
Alliance Path	Holds the root path, where the directories path to be created.
Handler	Holds the activation string, which needs to be passed as a parameter to the CALLJEE.

Outward Message Processing through File Process

You need to set the MQ Enable field to None for processing of message for the file present in the Alliance Path of SWIFT.ALLIANCE.PARAM. Ensure a valid setup in the SWIFT.ALLIANCE.PARAM parameter table for Outward processing of SWIFT messages.

Outward Message Processing through MQ Server

You need to set the MQ Enable field to Outward for processing respective Swift messages. The Handler field holds the activation string, which has to be passed as a parameter to the CALLJEE and is used in TAFC runtime. Ensure a valid setup in the SWIFT.ALLIANCE.PARAM parameter table for Inward or Outward processing of Swift messages.